HSC Information Processes and Technology Assessment Task 3: Marking Criteria
UNDERSTANDING THE PROBLEM (H2.1, H6.1, H7.2)
Marks
Criteria
8-10
Identifies and provides a clear and comprehensive problem definition
Provides an extensive preliminary investigation, detailing whether or not the solution to the problem can be solved quickly
5-7
Identifies and provides a thorough problem definition
Provides an thorough preliminary investigation, detailing whether or not the solution to the problem can be solved quickly
3-5
Provides a broad problem definition, without a clear comprehension of the problem
Provides a broad preliminary investigation, detailing whether or not the solution to the problem can be solved quickly
1-3
Provides a limited problem definition, without a clear comprehension of the problem
Provides a poor preliminary investigation, detailing whether or not the solution to the problem can be solved quickly
PLANNING (H2.1, H2.2, H6.1, H6.2, H7.2)
Marks
Criteria
8-10
Provides a clear and comprehensive feasibility study containing a requirement report, feasibility of the new system and recommendations for the new system
Provides a comprehensive description of the design specifications for the new system
5-7
Provides a detailed feasibility study containing a requirement report, feasibility of the new system and recommendations for the new system
Provides a thorough description of the design specifications for the new system
3-5
Provides a broad feasibility study containing a requirement report, feasibility of the new system and recommendations for the new system
Provides a broad description of the design specifications for the new system
1-3
Provides a limited study containing a requirement report, feasibility of the new system and recommendations for the new system
Provides a limited description of the design specifications for the new system
DESIGNING (H2.2, H6.1, H6.2, H7.2)
Marks
Criteria
8-10
Provides a clear and comprehensive Data Flow Diagram (DFD) containing all required entities and correct data flows
Provides a complete Entity Related Diagram (ERD) consisting of various tables and their relationships
Provides a comprehensive description of five queries used in the database (three of which involve relationships)
5-7
Provides a detailed Data Flow Diagram (DFD) containing most required entities and correct data flows
Provides a thorough Entity Related Diagram (ERD) consisting of various tables and their relationships
Provides a thorough description of four to five queries used in the database (two to three of which involve relationships)
3-5
Provides a broad Data Flow Diagram (DFD) containing some required entities and few correct data flows
Provides a satisfactory Entity Related Diagram (ERD) consisting of a limited number of tables and some relationships
Provides a broad description of three to four queries used in the database (one to two of which involve relationships)
1-3
Provides a limited Data Flow Diagram (DFD) containing little of the required entities and no correct data flows
Provides a poor Entity Related Diagram (ERD) consisting of few tables with little or no relationships
Provides a limited description of less than a total of two queries used in the database which may involve relationships
IMPLEMENTING (H6.2, H7.1)
Marks
Criteria
4-5
Provides a clear and comprehensive explanation of the method of conversion to be used in the new system
Provides a critical analysis of the reasoning behind choosing the method of conversion
2-4
Provides a thorough explanation of the method of conversion to be used in the new system
Provides a detailed analysis of the reasoning behind choosing the method of conversion
1-2
Provides a satisfactory explanation of the method of conversion to be used in the new system
Provides a limited analysis of the reasoning behind choosing the method of conversion
TESTING, EVALUATING, MAINTAINING (H6.1, H7.2)
Marks
Criteria
4-5
Provides a clear and comprehensive description of the types of testing and evaluation to be used in the new system
Provides a critical analysis of the reasoning behind choosing the methods of testing and evaluation
Provides a comprehensive evaluation of whether or not the initial needs of the new system were met
2-4
Provides a thorough description of the types of testing and evaluation to be used in the new system
Provides a detailed analysis of the reasoning behind choosing the methods of testing and evaluation
Provides a thorough evaluation of whether or not the initial needs of the new system were met
1-2
Provides a satisfactory description of the types of testing and evaluation to be used in the new system
Provides a limited analysis of the reasoning behind choosing the methods of testing and evaluation
Provides a limited evaluation of whether or not the initial needs of the new system were met
Total Marks for Documentation:
General Comments
PRACTICAL COMPONENT (H1.1)
Marks
Criteria
12-15
Provides a clear and comprehensive database for the online music store
Provides a complete number of tables with sample entries
Demonstrates a number of relationships between various tables
Provides a comprehensive description of five queries used in the database (three of which involve relationships)
Can be viewed in Microsoft Access 2007
9-12
Provides a detailed database for the online music store
Provides a thorough number of tables with sample entries
Demonstrates a number of relationships between most tables
Provides a thorough description of four to five queries used in the database (two to three of which involve relationships)
Can be viewed in Microsoft Access 2007
5-9
Provides a broad database for the online music store
Provides a satisfactory number of tables with a limited number of sample entries
Demonstrates a limited number or relationships between some tables
Provides a broad description of three to four queries used in the database (one to two of which involve relationships)
Can be viewed in Microsoft Access 2007
1-4
Provides a limited database for the online music store
Provides a poor number of tables with little or no sample entries
Demonstrates little or no relationships between tables
Provides a limited description of less than a total of two queries used in the database which may involve relationships
Cannot be viewed in Microsoft Access 2007
Total Marks for Practical Component:
General Comments:
Total Marks for Assessment Task 4: /60 /25%
Assessment Task 3: Allocated Marks
Marks
Task Requirement
3 7
7
3
2 3 5
5
5 5
15
Documentation · UNDERSTANDING THE PROBLEM (H2.1, H6.1, H7.2) o Preliminary Investigation (150 words) o Problem Definition (200 words)
· PLANNING (H2.1, H2.2, H6.1, H6.2, H7.2) o A feasibility study: § Requirement Report (200 words) § Feasibility of the new system (technical feasibility, schedule feasibility only) (250 words) § Recommendations for the new system (200 words) o Design Specifications for the database (Can be in bullet points 100 words)
· DESIGNING (H2.2, H6.1, H6.2, H7.2) o A Data Flow Diagram for Searching for videos and DVDs in the store (1 page) o An Entity Related Diagram (ERD) (This can be printed straight from Microsoft Access) o A description of at LEAST five queries used in your database. (Three of these queries must involve relationships between tables in the database)
· IMPLEMENTING (H6.2, H7.1) o Explanation of the method of conversion to be used when implementing the new system into the online music store (200 words)
· TESTING, EVALUATING, MAINTAINING (H6.1, H7.2) o Brief description of the testing and evaluation of the new system (300 words) o Evaluation of whether or not initial needs were met through the development of the new system (150 words)
Practical Component (H1.1) · Construct a database which could be implemented in the online music store. This relational database should be developed using Microsoft Access 2007, and should contain a minimum of five queries and a number of related tables.
HSC Information Processes and Technology
Assessment Task 3: Marking Criteria
UNDERSTANDING THE PROBLEM (H2.1, H6.1, H7.2)
PLANNING (H2.1, H2.2, H6.1, H6.2, H7.2)
DESIGNING (H2.2, H6.1, H6.2, H7.2)
IMPLEMENTING (H6.2, H7.1)
TESTING, EVALUATING, MAINTAINING (H6.1, H7.2)
Total Marks for Documentation:
General Comments
PRACTICAL COMPONENT (H1.1)
Total Marks for Practical Component:
General Comments:
Total Marks for Assessment Task 4: /60
/25%
Assessment Task 3: Allocated Marks
7
7
3
2
3
5
5
5
5
15
· UNDERSTANDING THE PROBLEM (H2.1, H6.1, H7.2)
o Preliminary Investigation (150 words)
o Problem Definition (200 words)
· PLANNING (H2.1, H2.2, H6.1, H6.2, H7.2)
o A feasibility study:
§ Requirement Report (200 words)
§ Feasibility of the new system (technical feasibility, schedule feasibility only) (250 words)
§ Recommendations for the new system (200 words)
o Design Specifications for the database (Can be in bullet points 100 words)
· DESIGNING (H2.2, H6.1, H6.2, H7.2)
o A Data Flow Diagram for Searching for videos and DVDs in the store (1 page)
o An Entity Related Diagram (ERD) (This can be printed straight from Microsoft Access)
o A description of at LEAST five queries used in your database. (Three of these queries must involve relationships between tables in the database)
· IMPLEMENTING (H6.2, H7.1)
o Explanation of the method of conversion to be used when implementing the new system into the online music store (200 words)
· TESTING, EVALUATING, MAINTAINING (H6.1, H7.2)
o Brief description of the testing and evaluation of the new system (300 words)
o Evaluation of whether or not initial needs were met through the development of the new system (150 words)
Practical Component (H1.1)
· Construct a database which could be implemented in the online music store. This relational database should be developed using Microsoft Access 2007, and should contain a minimum of five queries and a number of related tables.